Clean Architecture
- Downloads：8681
- Type：Epub+TxT+PDF+Mobi
- Create Date：2021-03-06 03:15:37
- Update Date：2025-09-07
- Status：finish
- Author：Robert C. Martin
- ISBN：0134494164
- Environment：PC/Android/iPhone/iPad/Kindle
- Download
Summary
Building upon the success of best-sellers The Clean Coder and Clean Code， legendary software craftsman Robert C。 "Uncle Bob" Martin shows how to bring greater professionalism and discipline to application architecture and design。
As with his other books， Martin's Clean Architecture doesn't merely present multiple choices and options， and say "use your best judgment": it tells you what choices to make， and why those choices are critical to your success。 Martin offers direct， no-nonsense answers to key architecture and design questions like:
What are the best high level structures for different kinds of applications， including web， database， thick-client， console， and embedded apps？
What are the core principles of software architecture？
What is the role of the architect， and what is he/she really trying to achieve？
What are the core principles of software design？
How do designs and architectures go wrong， and what can you do about it？
What are the disciplines and practices of professional architects and designers？
Clean Architecture is essential reading for every software architect， systems analyst， system designer， and software manager — and for any programmer who aspires to these roles or is impacted by their work。
As with his other books， Martin's Clean Architecture doesn't merely present multiple choices and options， and say "use your best judgment": it tells you what choices to make， and why those choices are critical to your success。 Martin offers direct， no-nonsense answers to key architecture and design questions like:
What are the best high level structures for different kinds of applications， including web， database， thick-client， console， and embedded apps？
What are the core principles of software architecture？
What is the role of the architect， and what is he/she really trying to achieve？
What are the core principles of software design？
How do designs and architectures go wrong， and what can you do about it？
What are the disciplines and practices of professional architects and designers？
Clean Architecture is essential reading for every software architect， systems analyst， system designer， and software manager — and for any programmer who aspires to these roles or is impacted by their work。
Reviews
Carlos Villarroel
，
Excellent book by Uncle Bob， much faster to read than Clean Code and with very good examples and patterns to be able to generate a sustainable and scalable architecture， the importance of understanding the essentials when defining an architecture versus those decisions that you can and should postpone。 as much as possible as they shouldn't influence your system as such。 Clean Architecture is another compulsory reading that is worth reviewing from time to time， decoupling， refactoring， scaling ar Excellent book by Uncle Bob， much faster to read than Clean Code and with very good examples and patterns to be able to generate a sustainable and scalable architecture， the importance of understanding the essentials when defining an architecture versus those decisions that you can and should postpone。 as much as possible as they shouldn't influence your system as such。 Clean Architecture is another compulsory reading that is worth reviewing from time to time， decoupling， refactoring， scaling are extremely important but must always be done with a strategy and understanding for whom it is carried out and what is its objective。 。。。more
Tanya
，
Very impractical book， full of memories from 80s。
Melania Andrisan
，
This review has been hidden because it contains spoilers。 To view it， click here。 I've listen to Uncle Bob's talks and read his articles before so this book comes with no surprises。 Also is good to mention that he is just highlighting the principles in this book and how they will end up in the architecture of a system， he is not going in depth in non of them， so if you are not familiar with them is better to find another book to learn them first。 What he is showing in the book is how even though you know the principles the thinks can get wild。 He takes a logical path of going I've listen to Uncle Bob's talks and read his articles before so this book comes with no surprises。 Also is good to mention that he is just highlighting the principles in this book and how they will end up in the architecture of a system， he is not going in depth in non of them， so if you are not familiar with them is better to find another book to learn them first。 What he is showing in the book is how even though you know the principles the thinks can get wild。 He takes a logical path of going through OOP， putting a big accent on polymorphism （dependency invention）， than moves into functional programing and immutability （with the emphases on concurrency） and immediately after into design patterns and principles by starting with SOLID， but not just how they translate into code， but how they translate into components too。 All of this to make clear to everyone that the plugin architecture is an approach that will work in 90% of the cases and will save everyone a lot to time。But， I think， what I liked the most were the examples， the history of programming as well as the personal experiences Uncle Bob had in his developer life starting with assembler， continuing with C， C++， Java。。。 Below are some notes I too that might be useful and also a starting point to learn more for a novice reader。The constrains we need to manage:- Structured programming is discipline imposed upon direct transfer of control。- Object-oriented programming is discipline imposed upon indirect transfer of control。- Functional programming is discipline imposed upon variable assignment。SOLID （principles that tolerate change， are easy to understand and and are basic components that can be used in may software systems）:- SRP: The Single Responsibility Principle - one reason to change， separate the code that different actors depend one- OCP: The Open-Close Principle - open to add new code - open for extension but close for modification -> This goal is accomplished by partitioning the system into components， and arranging those components into a dependency hierarchy that protects higher-level components from changes in lower-level components。- LSP: The Liskov Substitution Principle - interchangeable parts must adhere to a contract - ISP: The Interface Segregation Principle - avoid depending on things that you do not use- DIP: The Dependency Invention Principle - details （low-level） should depend on policies（high-level） - also， source code dependencies refer only to abstractions， not to concretions if that dependency is not stable （Abstract Factories）。 This is one of the most mentioned principles in the book。 Components - map for build-ability and maintainability Principles of Component cohesion （basically the pollers you need to balance）: - REP （Group for reuse）: The Reuse/Release Equivalent Principles - the granule of reuse is the granule of release- CPP （Group for maintenance）: The Common Closure Principle - （SRP+OCP） Gather into components those classes that change for the same reasons and at the same times。 Separate into different components those classes that change at different times and for different reasons。- CRP （Split to avoid unneeded releases）: The Common Reuse Principle - （ISP） Don’t force users of a component to depend on things they don’t need。Principles of Component coupling:- ADP: The Acyclic Dependencies Principle - Allow no cycles in the component dependency graph - SDP: Stable Dependencies Principle - Depend in the direction of stability （modules that are intended to be changed are not dependent on by modules that are harder to change）- SAP: Stable Abstraction Principle - A component should be as abstract as it is stable （stable components should be abstract， unstable components should be concrete since it its instability allows the concrete code within it to be easily changed。 。。。more
Anton
，
A very clean book about clean architecture :） The book was easy to follow， the examples were on point。 Highly recommend it to software developers of any level。
Steven Weler
，
Unglaublich bereichernd！
Michal Kardyś
，
While it's not in-depth guide about software architecture， the book presents great principles to follow by - a solid foundation。 While it's not in-depth guide about software architecture， the book presents great principles to follow by - a solid foundation。 。。。more
Thiago Lopes
，
Ótimo livro sobre como criar um arquitetura limpa e testável
Abhishek
，
First book of its kind - somehow the author has managed to make complex organizational and architectural concepts read like a fun storyline。 He switches between high level to low level details and team implications without missing a beat。 His ideas are meaningful and powerful and mostly practical。 He is also pragmatic in coming out advice， acknowledging the complex world we live in where architectural decisions are often dictated by financial and market constraints or demands。 Even then， his app First book of its kind - somehow the author has managed to make complex organizational and architectural concepts read like a fun storyline。 He switches between high level to low level details and team implications without missing a beat。 His ideas are meaningful and powerful and mostly practical。 He is also pragmatic in coming out advice， acknowledging the complex world we live in where architectural decisions are often dictated by financial and market constraints or demands。 Even then， his approach shows a way to do things in a better way。 I truly enjoyed reading the book and learned a lot from it。 The first half seemed more informative than the latter part but it’s a good read over all。 It is already informing some of my design decisions。 One thing that would have been helpful is to include a summary of key take always at the end for easy reference。 。。。more
Deeptha Rangarajan
，
I was very impressed with "Clean code"。 It gave me practical tips to write better code the same day！ Naturally， I had high expectations for this book。 There is a lot of good information in this book but I find most of the chapters explained design concepts from a very high level， leaving so much room for interpretation and I don't think it had to be that way。 There are so many missed opportunities in this book where the author had started on common design problems but did not end up giving concr I was very impressed with "Clean code"。 It gave me practical tips to write better code the same day！ Naturally， I had high expectations for this book。 There is a lot of good information in this book but I find most of the chapters explained design concepts from a very high level， leaving so much room for interpretation and I don't think it had to be that way。 There are so many missed opportunities in this book where the author had started on common design problems but did not end up giving concrete options to solve them。 I wish the book had code that came from a bad design and one that came from a better design to illustrate the high level concepts better。 。。。more
Jason Bonafide
，
A must read for anybody looking to become a better Software Engineer and/or ArchitectThis book provides a ton of valuable information。 The author does an amazing job of describing what clean architecture is， why architecture must be clean and how to achieve it。 While I've taken a lot away from my first read， I fully expect to give it another read as there is so much good detail to grasp and I want to get the most out of this book。 I highly recommend this book！ A must read for anybody looking to become a better Software Engineer and/or ArchitectThis book provides a ton of valuable information。 The author does an amazing job of describing what clean architecture is， why architecture must be clean and how to achieve it。 While I've taken a lot away from my first read， I fully expect to give it another read as there is so much good detail to grasp and I want to get the most out of this book。 I highly recommend this book！ 。。。more
Özgül Ezgin
，
Great book 👏🏻 I love Uncle Bob’s books。。 Definatly a must read。。
Jeffrey Chang
，
Must read as a software engineer。
Jason Kim
，
Lots of wisdom on software architecture。
Daniel Assis Alfenas
，
A very good book， even if it is a little slow and go very little into practice of how an architecture evolves through a real project。 The perspective of knowing what the use cases are before designing your system is unrealistic; most of use cases users will use for real are not mapped from beginning （that is one reason why use case analysis is unpractical）。 Instead， the book could show how use cases come and go discarded and how you can handle this considering trade-offs to encapsulate stuff in A very good book， even if it is a little slow and go very little into practice of how an architecture evolves through a real project。 The perspective of knowing what the use cases are before designing your system is unrealistic; most of use cases users will use for real are not mapped from beginning （that is one reason why use case analysis is unpractical）。 Instead， the book could show how use cases come and go discarded and how you can handle this considering trade-offs to encapsulate stuff in one way or other， with ports and adapter or any other option。 。。。more
Damian Piątkowski
，
Really nice anecdotes about history of struggle with software development and nothing else。
Filippo Pacifici
，
This is a useful book。 Many design principles explained are discussed in depth both around components design and architectural principles。There are two downsides I can think about。- some areas feel shallow and disconnected from each other （specifically in part IV - architecture。 This is a lot less deep and thorough than the parts about components and design）- some practices feel a bit outdated。
Jeffrey Cao
，
The main message I got out of this book was organize your code in a way that makes adding additional code in the future the easiest
Guillermo Ortiz
，
Must read for everyone working in the software craftmanship。 Not just for architects but extremely useful for developers and similar profiles。 Love the simple writing and explanation。
José Ramírez De La Rosa
，
Overall， a fantastic book which leveled up my career。 However， just as with Clean Code， take it with a grain of salt。
Gustav Staprans
，
Great book。 Just the right amount of depth。
Kyle Hamilton
，
Great resource that's worth reading， but the transition between sections seemed a little disjointed to me。 Great resource that's worth reading， but the transition between sections seemed a little disjointed to me。 。。。more
Michael
，
Uncle Bob's stance on software architecture。 A language agnostic book describing the key principles a good （and "clean"） software should be built around。 Since its publication， the SOLID architecture principles introduced in this book have become industry standards and shall be known by any expeerienced software programmer。 Uncle Bob's stance on software architecture。 A language agnostic book describing the key principles a good （and "clean"） software should be built around。 Since its publication， the SOLID architecture principles introduced in this book have become industry standards and shall be known by any expeerienced software programmer。 。。。more
Maksim Vasileuski
，
Неплохая книга об основах архитектуры и паттернах。 Ожидал большей глубины и прикладного контента， на деле вышло довольно поверхностно。 Но написано доходчиво и легко。8/10
Daniel
，
A great read on software architecture design and principles。This was a really comprehensive outlook on software architecture and as this was my first read on the subject， I can say with confidence that I understood a fair amount of the concepts and concerns that Rober Martin tried to communicate in this great book。He looks at the SOLID principles and components principles like cohesion and coupling from the architectural perspective and how we can apply them in our higher-level designs。 After th A great read on software architecture design and principles。This was a really comprehensive outlook on software architecture and as this was my first read on the subject， I can say with confidence that I understood a fair amount of the concepts and concerns that Rober Martin tried to communicate in this great book。He looks at the SOLID principles and components principles like cohesion and coupling from the architectural perspective and how we can apply them in our higher-level designs。 After that， he tries to depict a bigger picture to express the general concerns of the software architects in development， deployment， operation， and maintenance parts。 He puts a big emphasis on keeping the options open when it comes to details like choosing a database， framework， or even our I/O device/platform。He argues about considering an independent design in different aspects of our system like use cases， operation， development， deployment and he makes his case for independent develop-ability and deploy-ability。 Then he stumbles upon software decoupling modes。I really enjoyed it。 And I recommend it to those who want to know more about creating software that can last longer in this fast-changing tech phase of the digital revolution。 。。。more
Alan Tavares
，
Muito recomendado para estrutura de aplicações。Ótima leitura e grande conhecimento compartilhado pelo Robert Martin。Não vou dar spoilers mas vale muito a leitura para área de desenvolvimento assim como os demais livros similares como clean code e clean coders。
Stefan Papp
，
S。O。L。I。D。 principles are described in terms of how they affect the architecture （by constricting options and enforcing rules） which is refreshing compared to the usual definition drop。 Some good advice and simple metrics make this a casual but enjoyable read， certainly a great appetizer for Fowler's work - which the author greatly encourages。Not a definitive reference but， as with Clean Code， a very solid guidebook to advise the newcomer on the subject。 As always， literal interpretation will po S。O。L。I。D。 principles are described in terms of how they affect the architecture （by constricting options and enforcing rules） which is refreshing compared to the usual definition drop。 Some good advice and simple metrics make this a casual but enjoyable read， certainly a great appetizer for Fowler's work - which the author greatly encourages。Not a definitive reference but， as with Clean Code， a very solid guidebook to advise the newcomer on the subject。 As always， literal interpretation will poison the valuable lessons inside。 Enjoy with moderation！ 。。。more
Alb85
，
Dopo aver letto il classico Clean Code: Guida per diventare bravi artigiani nello sviluppo agile di software di Robert C。 Martin （detto Uncle Bob）， mi aspettavo di più da questo libro。Il libro è sostanzialmente diviso in due parti。 Nella prima vengono menzionati una valanga di principi di programmazione: Single Responsibility Principle， Open-Closed Principlem， Liskov Substitution Principle， Interface Segregation Principle… mi fermo qui che altrimenti supero il limite di caratteri consentito。 Que Dopo aver letto il classico Clean Code: Guida per diventare bravi artigiani nello sviluppo agile di software di Robert C。 Martin （detto Uncle Bob）， mi aspettavo di più da questo libro。Il libro è sostanzialmente diviso in due parti。 Nella prima vengono menzionati una valanga di principi di programmazione: Single Responsibility Principle， Open-Closed Principlem， Liskov Substitution Principle， Interface Segregation Principle… mi fermo qui che altrimenti supero il limite di caratteri consentito。 Questi principi sono sicuramente utili。 Purtroppo， vengono spiegati in una paginetta l’uno， quindi i concetti diventano poco concreti e difficili da ricordare。 Avrei preferito trovare meno principi， i più importanti， con più esempi concreti。La seconda parte è più interessante ed essenzialmente spiega l’importanza di un’architettura software: definire le regole operative e tralasciare i dettagli （come i tipi di database come SQL， il web， la GUI， i framework）。In sintesi， libro troppo astratto che vuole spiegare troppo。Spunti interessanti:- La matrice di Eisenhower。 “classifica” delle priorità:t1。 urgente e importante;t2。 non urgente， ma importante;t3。 urgente， ma non importante;t4。 non urgente e neanche importante。Architettura del software è importante， il comportamento del software è urgente。 。。。more
andrew
，
Surprisingly clairvoyant
AnhDuc
，
A few things I learned after reading this books: - Software architecture should focus on core business， not details- Good architecture should allow changes- Good should know the good line between each components of our architecture so that they can be changed Pluggable architecture should be supported。- Should not let architecture slow the business that you aren't able to deliver anything- Know distinctions between layers on software， hardware， OS， firmwareI think the general ideas of the book a A few things I learned after reading this books: - Software architecture should focus on core business， not details- Good architecture should allow changes- Good should know the good line between each components of our architecture so that they can be changed Pluggable architecture should be supported。- Should not let architecture slow the business that you aren't able to deliver anything- Know distinctions between layers on software， hardware， OS， firmwareI think the general ideas of the book are really good knowledge to have when building softwares。 I find some chapters are not well-written and I don't really learn anything from it。 。。。more
Michael Vaughan
，
There are some pages that made me scratch my head a bit， especially early on when he implies that LOC added is related to developer productivity。 However， there is good advice given related to architecting a software system that separates higher level business rules from lower level details。
Reference
google book https://www.google.com/search?tbm=bks&q=Clean Architecture
hathitrust digital library https://babel.hathitrust.org/cgi/ls?q1=Clean Architecture&field1=ocr&a=srchls&ft=ft&lmt=ft
The British Library https://bll01.primo.exlibrisgroup.com/discovery/search?query=any,contains,Clean Architecture&tab=LibraryCatalog&search_scope=Not_BL_Suppress&vid=44BL_INST:BLL01&lang=en&offset=0